Skip to content

test: add full-binary integration suite - #88

Open
P4ST4S wants to merge 1 commit into
integration/v1.2-securityfrom
test/full-binary-e2e-50
Open

test: add full-binary integration suite#88
P4ST4S wants to merge 1 commit into
integration/v1.2-securityfrom
test/full-binary-e2e-50

Conversation

@P4ST4S

@P4ST4S P4ST4S commented Aug 24, 2026

Copy link
Copy Markdown
Owner

Summary

  • build the proxy and a controllable stdio upstream once per integration suite
  • exercise real stdio and HTTP subprocesses, including policy, rate limits, redaction, terminal audit outcomes, MCP 2026 metadata, static and OIDC authentication, incoming TLS, and JSONL/SQLite verification
  • keep the suite opt-in with the integration build tag and run it in CI

Context

Closes #50

This PR is stacked on the temporary v1.2 integration branch so it can cover every preceding security workstream. It can be retargeted to main after the dependency PRs merge.

Test plan

  • GOCACHE=/tmp/mcp-audit-go-cache go test -race ./...
  • GOCACHE=/tmp/mcp-audit-go-cache go test -tags=integration ./tests/integration/...
  • GOCACHE=/tmp/mcp-audit-go-cache go build ./...
  • GOCACHE=/tmp/mcp-audit-go-cache go vet ./...

The integration suite completes in about six seconds locally.

Stability impact

None. This adds opt-in tests and a CI step without changing runtime contracts.

@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants